View Issue Details

IDProjectCategoryView StatusLast Update
0001150T99X171.00 SKB EagleSWpublic2021-12-23 16:36
Reporter(ALTech) Younkwang Jung Assigned To(ALTech) Younkwang Jung Due Date
PriorityurgentSeveritys2-severeReproducibilityrandom
Status closedResolutionfixed 
Summary0001150: [BFX_AT100][BTF] Issue where the resolution of STB was changed to 720P after power booting
DescriptionHi kerwin

FW : v15.522.57 ( test3 version )
        I heard that this issue has occurred before.

The original resolution is 2160p60hz.
After power boot, resolution became 720p60hz.
Then the resolution was changed to 2160p60hz after disonnect/connect the HDMI cable.

I attached log file
Please check this issue.

..
02-21 15:09:26.413 3466 3611 D SystemControl: [CPQControl]:SetCurrentSourceInputInfo: hdr status is 0!
02-21 15:09:26.413 3466 3611 D SystemControl: [CPQControl]:CheckOutPutMode: current output mode is 720p60hz!
02-21 15:09:26.413 3466 3611 D SystemControl: [CPQControl]:CheckOutPutMode: size is 8, str is : 720p!
02-21 15:09:26.413 3466 3611 D SystemControl: [CPQControl]:CheckOutPutMode: inputFrameHeight: 1080, outputFrameHeight: 720!
02-21 15:09:26.413 3466 3611 D SystemControl: [CPQControl]:CheckOutPutMode: output mode is 13!
02-21 15:09:26.413 3466 3611 D SystemControl: [CPQControl]:SetCurrentSourceInputInfo: same signal, no need set!
..
02-21 15:10:55.882 4007 5291 I SystemControlEvent: system control callback event: 4
02-21 15:10:55.882 5788 5906 E UEI.SmartControl: Unable to find XML file (1th trial) /data/btv_home/tmp/hdmi-edid.xml
..

Thank you
YK.Jung
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (ALTech) SY Yoon , (SW) River Wong

Activities

(ALTech) Younkwang Jung

2021-02-21 14:36

developer  

logcat_hdmi_720p_issue.log (5,494,173 bytes)

(ALTech) Younkwang Jung

2021-03-03 17:01

developer   ~0006212

Last edited: 2021-03-03 17:03

View 3 revisions

Hi Kerwin

The sleep mode on/off test is in progress using the integrated power button of the RCU.
But during the test, we found that the resolution of the TV video was changed. please check the attached log. (logcat.zip )
The last part of the attached log is marked 720P on TV.

and if I search with "current output mode" string, it shows as follows. ( I marked only a few representative ones. )
Is there no problem?

03-03 10:45:30.054 3452 3603 D SystemControl: [CPQControl]:CheckOutPutMode: current output mode is null!
..
03-03 10:45:30.144 3452 3603 D SystemControl: [CPQControl]:CheckOutPutMode: current output mode is 720p60hz!
..
03-03 10:53:00.041 3452 3603 D SystemControl: [CPQControl]:CheckOutPutMode: current output mode is 2160p60hz!
..
03-03 11:22:04.336 3452 3603 D SystemControl: [CPQControl]:CheckOutPutMode: current output mode is 576cvbs!
..
03-03 14:14:42.324 3452 3603 D SystemControl: [CPQControl]:CheckOutPutMode: current output mode is 480p60hz!
..

Please check it
Thanks
YK.Jung

(ALTech) Younkwang Jung

2021-03-03 17:03

developer   ~0006213

Hi Kerwin

Sorry , I attached the file here.

Thank you
YK.Jung
logcat.zip (11,219,604 bytes)

(SW) Kerwin Chen

2021-03-05 08:57

developer   ~0006234

Hi Mr. YK Jung,

From the log file, the reason STB set resolution to 720p is that TV's EDID has incorrect value.
But I can't tell why the EDID is wrong after several times of standby/resume aging test.
Sometimes TV needs time to prepare EDID information.
I guess if you increase the interval to do standby/resume aging test, issue may not happen.

============= EDID OK ==================================
03-03 10:24:26.808 0 0 I : [ 2167.688089@1] 00ffffffffffff004c2d140f000e0001011c0103805f36780a23ada4544d9926
03-03 10:24:26.808 0 0 I : [ 2167.688089@1] 0f474abdef80714f81c0810081809500a9c0b300010108e80030f2705a80b058
03-03 10:24:26.808 0 0 I : [ 2167.688089@1] 8a00501d7400001e023a801871382d40582c4500501d7400001e000000fd0018
03-03 10:24:26.808 0 0 I : [ 2167.688089@1] 4b0f873c000a202020202020000000fc0053414d53554e470a2020202020016d
03-03 10:24:26.808 0 0 I : [ 2167.688089@1]
03-03 10:24:26.808 0 0 I : [ 2167.688089@1]
03-03 10:24:26.808 0 0 I [ 2167.688092@1] hdmitx: edid: blk1 raw data
03-03 10:24:26.808 0 0 I [ 2167.688116@1] hdmitx: edid:
03-03 10:24:26.808 0 0 I : [ 2167.688116@1] 020356f05761101f041305142021225d5e5f6065666263640716031229090707
03-03 10:24:26.808 0 0 I : [ 2167.688116@1] 15075057070183010000e2004fe305c3016e030c002000b83c20008001020304
03-03 10:24:26.808 0 0 I : [ 2167.688116@1] 67d85dc401788003e3060d01e30f01e0e5018b849001011d80d0721c1620102c
03-03 10:24:26.808 0 0 I : [ 2167.688116@1] 2580501d7400009e662156aa51001e30468f3300501d7400001e000000000089

========= EDID not OK =================
03-03 10:39:16.735 0 0 I : [ 3057.613089@0] 00ffffffffffff004c2d140f000e0001011c0103805f36780a23ada4544d9926
03-03 10:39:16.735 0 0 I : [ 3057.613089@0] 0f474abdef80714f81c0810081809500a9c0b300010108e80030f2705a80b058
03-03 10:39:16.735 0 0 I : [ 3057.613089@0] 8a00501d7400001e023a801871382d40582c4500501d7400001e000000fd0018
03-03 10:39:16.735 0 0 I : [ 3057.613089@0] 4b0f873c000a202020202020000000fc0053414d53554e470a2020202020016d
03-03 10:39:16.735 0 0 I : [ 3057.613089@0]
03-03 10:39:16.735 0 0 I : [ 3057.613089@0]
03-03 10:39:16.735 0 0 I [ 3057.613092@0] hdmitx: edid: blk1 raw data
03-03 10:39:16.735 0 0 I [ 3057.613115@0] hdmitx: edid:
03-03 10:39:16.735 0 0 I : [ 3057.613115@0] 020356f05761101f041305142021225d041305142021225d0716031229090707
03-03 10:39:16.735 0 0 I : [ 3057.613115@0] 15075057070183010000e2004fe305c3016e030c002000b83c20008001020304
03-03 10:39:16.735 0 0 I : [ 3057.613115@0] 67d85dc401788003e3060d01e30f01e0e5018b849001011d80d0721c1620102c
03-03 10:39:16.735 0 0 I : [ 3057.613115@0] 0000000000000000000000000000000000000000000000000000000000000000
03-03 10:39:16.735 0 0 I : [ 3057.613115@0]
03-03 10:39:16.735 0 0 I : [ 3057.613115@0]
03-03 10:39:16.735 0 0 I [ 3057.613117@0] hdmitx: edid: check sum invalid
03-03 10:39:16.735 0 0 I [ 3057.613119@0] hdmitx: edid: check sum invalid
03-03 10:39:16.735 0 0 I [ 3057.613122@0] hdmitx: edid: blk0 raw data
03-03 10:39:16.735 0 0 I [ 3057.613145@0] hdmitx: edid:
03-03 10:39:16.735 0 0 I : [ 3057.613145@0] 00ffffffffffff004c2d140f000e000101000000000000000000000000000000
03-03 10:39:16.735 0 0 I : [ 3057.613145@0] 0000000000000000000000000000000000000000000000000000000000000000
03-03 10:39:16.735 0 0 I : [ 3057.613145@0] 01000000000000000000000000000000ffffffffffff06000000000000000000
03-03 10:39:16.735 0 0 I : [ 3057.613145@0] 0000000000000000000000000000000000000000000000000000000000000000
03-03 10:39:16.735 0 0 I : [ 3057.613145@0]
03-03 10:39:16.735 0 0 I : [ 3057.613145@0]
03-03 10:39:16.735 0 0 I [ 3057.613147@0] hdmitx: edid: blk1 raw data
03-03 10:39:16.735 0 0 I [ 3057.613170@0] hdmitx: edid:
03-03 10:39:16.735 0 0 I : [ 3057.613170@0] 020356f05761101f041305142021225d5e5f6065666263640716031229090707
03-03 10:39:16.735 0 0 I : [ 3057.613170@0] 15075057070183010000e2004fe305c3016e030c002000b83c20008001020304
03-03 10:39:16.735 0 0 I : [ 3057.613170@0] 67d85dc40178800367d85dc40178800367d85dc40178800367d85dc401788003
03-03 10:39:16.735 0 0 I : [ 3057.613170@0] 67d85dc40178800367d85dc40178800367d85dc40178800367d85dc401788003
03-03 10:39:16.735 0 0 I : [ 3057.613170@0]
03-03 10:39:16.735 0 0 I : [ 3057.613170@0]

(ALTech) Younkwang Jung

2021-03-05 09:28

developer   ~0006237

Last edited: 2021-03-05 09:28

View 2 revisions

Hi Kerwin

TV is LG TV
The resolution sometimes changes during the test and It also happens when QA tester wake up after being in sleep for a long time.

First of all, STB must read the EDID information accurately. (for example , once it fails, try again.)
If this EDID information is updated incorrectly, it will affect RCU issue.

I think this issue must be solved.
I hope to listen your opinion

Thank you
YK.jung

(SW) Kerwin Chen

2021-03-05 09:41

developer   ~0006238

Hi Mr. YK Jung,

From EDID information, it is Samsung TV.
Do you attach correct log for this issue ?

===== EDID parse result ============
00 ff ff ff ff ff ff 00 4c 2d 14 0f 00 0e 00 01
01 1c 01 03 80 5f 36 78 0a 23 ad a4 54 4d 99 26
0f 47 4a bd ef 80 71 4f 81 c0 81 00 81 80 95 00
a9 c0 b3 00 01 01 08 e8 00 30 f2 70 5a 80 b0 58
8a 00 50 1d 74 00 00 1e 02 3a 80 18 71 38 2d 40
58 2c 45 00 50 1d 74 00 00 1e 00 00 00 fd 00 18
4b 0f 87 3c 00 0a 20 20 20 20 20 20 00 00 00 fc
00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 6d

02 03 56 f0 57 61 10 1f 04 13 05 14 20 21 22 5d
5e 5f 60 65 66 62 63 64 07 16 03 12 29 09 07 07
15 07 50 57 07 01 83 01 00 00 e2 00 4f e3 05 c3
01 6e 03 0c 00 20 00 b8 3c 20 00 80 01 02 03 04
67 d8 5d c4 01 78 80 03 e3 06 0d 01 e3 0f 01 e0
e5 01 8b 84 90 01 01 1d 80 d0 72 1c 16 20 10 2c
25 80 50 1d 74 00 00 9e 66 21 56 aa 51 00 1e 30
46 8f 33 00 50 1d 74 00 00 1e 00 00 00 00 00 89
Block 0, Base EDID:
  EDID Structure Version & Revision: 1.3
  Vendor & Product Identification:
    Manufacturer: SAM
    Model: 3860
    Serial Number: 16780800
    Made in: week 1 of 2018
  Basic Display Parameters & Features:
    Digital display
    Maximum image size: 95 cm x 54 cm
    Gamma: 2.20
    RGB color display
    First detailed timing is preferred timing
  Color Characteristics:
    Red : 0.6406, 0.3300
    Green: 0.3007, 0.6005
    Blue : 0.1503, 0.0605
    White: 0.2802, 0.2900
  Established Timings I & II:
    IBM : 720x400 70.082 Hz 9:5 31.467 kHz 28.320 MHz
    DMT 0x04: 640x480 59.940 Hz 4:3 31.469 kHz 25.175 MHz
    Apple : 640x480 66.667 Hz 4:3 35.000 kHz 30.240 MHz
    DMT 0x05: 640x480 72.809 Hz 4:3 37.861 kHz 31.500 MHz
    DMT 0x06: 640x480 75.000 Hz 4:3 37.500 kHz 31.500 MHz
    DMT 0x09: 800x600 60.317 Hz 4:3 37.879 kHz 40.000 MHz
    DMT 0x0a: 800x600 72.188 Hz 4:3 48.077 kHz 50.000 MHz
    DMT 0x0b: 800x600 75.000 Hz 4:3 46.875 kHz 49.500 MHz
    Apple : 832x624 74.551 Hz 4:3 49.726 kHz 57.284 MHz
    DMT 0x10: 1024x768 60.004 Hz 4:3 48.363 kHz 65.000 MHz
    DMT 0x11: 1024x768 70.069 Hz 4:3 56.476 kHz 75.000 MHz
    DMT 0x12: 1024x768 75.029 Hz 4:3 60.023 kHz 78.750 MHz
    DMT 0x24: 1280x1024 75.025 Hz 5:4 79.976 kHz 135.000 MHz
    Apple : 1152x870 75.062 Hz 192:145 68.681 kHz 100.000 MHz
  Standard Timings:
    DMT 0x15: 1152x864 75.000 Hz 4:3 67.500 kHz 108.000 MHz
    DMT 0x55: 1280x720 60.000 Hz 16:9 45.000 kHz 74.250 MHz
    DMT 0x1c: 1280x800 59.810 Hz 16:10 49.702 kHz 83.500 MHz
    DMT 0x23: 1280x1024 60.020 Hz 5:4 63.981 kHz 108.000 MHz
    DMT 0x2f: 1440x900 59.887 Hz 16:10 55.935 kHz 106.500 MHz
    DMT 0x53: 1600x900 60.000 Hz 16:9 60.000 kHz 108.000 MHz (RB)
    DMT 0x3a: 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz
  Detailed Timing Descriptors:
    DTD 1: 3840x2160 60.000 Hz 16:9 135.000 kHz 594.000 MHz (1872 mm x 1053 mm)
                 Hfront 176 Hsync 88 Hback 296 Hpol P
                 Vfront 8 Vsync 10 Vback 72 Vpol P
    DTD 2: 1920x1080 60.000 Hz 16:9 67.500 kHz 148.500 MHz (1872 mm x 1053 mm)
                 Hfront 88 Hsync 44 Hback 148 Hpol P
                 Vfront 4 Vsync 5 Vback 36 Vpol P
  Display Range Limits:
    Monitor ranges (GTF): 24-75 Hz V, 15-135 kHz H, max dotclock 600 MHz
    Display Product Name: 'SAMSUNG'
  Extension blocks: 1
Checksum: 0x6d

(ALTech) Younkwang Jung

2021-03-05 10:28

developer   ~0006239

Hi Kerwin
Sorry , it's Samsung TV

Thanks you
YK.Jung

(ALTech) Younkwang Jung

2021-03-09 08:44

developer   ~0006267

Reminder sent to: (SW) Kerwin Chen

(SW) Kerwin Chen

2021-03-10 11:05

developer   ~0006278

Hi Mr. YK, Jung,

Could you check if issue still exists after you change to another TV HDMI port or HDMI cable ?
If EDID information is wrong, set resolution to 720p is the best workaround solution so far.

Thanks !

(ALTech) Younkwang Jung

2021-03-10 13:14

developer   ~0006283

Hi Kerwin

It is estimated that this issue is also related to RCU issue.
If EDID information is wrong , you should not simply set the resolution to 720p.
This issue must be resolved.

For your information>
When I was developing from the previous linux model,
When the edid information is wrong, I read it again up to 2 times.

Thanks!

(SW) Kerwin Chen

2021-03-10 14:47

developer   ~0006285

Hi Mr. YK, Jung,

Please check "https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1150#c6234".
Actually, EDID is read twice in driver but still have incorrect checksum.

Thanks !

(ALTech) Younkwang Jung

2021-03-10 15:06

developer   ~0006288

Hi Kerwin

OK , I see
As you know, the important thing is to read the EDID information accurately.
Please make sure that this part is clearly implemented.

Thanks!

(ALTech) Younkwang Jung

2021-03-12 13:12

developer   ~0006329

Reminder sent to: (SW) Kerwin Chen

(ALTech) Younkwang Jung

2021-03-19 10:21

developer   ~0006449

Reminder sent to: (SW) Kerwin Chen

(ALTech) Younkwang Jung

2021-04-06 13:50

developer   ~0006576

Reminder sent to: (SW) Kerwin Chen

(SW) Kerwin Chen

2021-04-06 14:39

developer   ~0006578

Hi Mr. YK, Jung,

What is problem for this Mantis issue ?

Per updated, AML already implements EDID checksum and read twice in current driver.

Thanks !

(ALTech) Younkwang Jung

2021-04-06 15:23

developer   ~0006581

Hi Kerwin

Then, is FW currently reading the edid information correctly?
When was that part modified in Amlogic?

Below is the VoC issue that was reported today.
https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1192

Please check it
Thanks

(SW) Kerwin Chen

2021-04-06 16:05

developer   ~0006584

Hi Mr. YK, Jung,

There are many possibilities to cause EDID read error.
What I said is from software point of view, current HDMI driver already read EDID twice.
Not all issues are SW problems, we need to check it case by case.
I will check Mantis 0001192 first.
Thanks !

(SW) Kerwin Chen

2021-12-23 16:36

developer   ~0009057

closed, not reproducible in recent version

Issue History

Date Modified Username Field Change
2021-02-21 14:36 (ALTech) Younkwang Jung New Issue
2021-02-21 14:36 (ALTech) Younkwang Jung Status new => assigned
2021-02-21 14:36 (ALTech) Younkwang Jung Assigned To => (SW) Kerwin Chen
2021-02-21 14:36 (ALTech) Younkwang Jung File Added: logcat_hdmi_720p_issue.log
2021-02-21 14:36 (ALTech) Younkwang Jung Issue Monitored: (SW) River Wong
2021-02-21 14:36 (ALTech) Younkwang Jung Issue Monitored: (ALTech) SY Yoon
2021-02-21 14:37 (ALTech) Younkwang Jung Summary [BFX_AT100][BTF] Issue where STB is changed to 720P after power booting => [BFX_AT100][BTF] Issue where the resolution of STB was changed to 720P after power booting
2021-02-21 14:37 (ALTech) Younkwang Jung Description Updated View Revisions
2021-03-03 17:01 (ALTech) Younkwang Jung Note Added: 0006212
2021-03-03 17:01 (ALTech) Younkwang Jung Note Edited: 0006212 View Revisions
2021-03-03 17:03 (ALTech) Younkwang Jung File Added: logcat.zip
2021-03-03 17:03 (ALTech) Younkwang Jung Note Added: 0006213
2021-03-03 17:03 (ALTech) Younkwang Jung Note Edited: 0006212 View Revisions
2021-03-03 17:04 (ALTech) Younkwang Jung Priority normal => urgent
2021-03-05 08:57 (SW) Kerwin Chen Note Added: 0006234
2021-03-05 09:28 (ALTech) Younkwang Jung Note Added: 0006237
2021-03-05 09:28 (ALTech) Younkwang Jung Note Edited: 0006237 View Revisions
2021-03-05 09:41 (SW) Kerwin Chen Note Added: 0006238
2021-03-05 10:28 (ALTech) Younkwang Jung Note Added: 0006239
2021-03-09 08:44 (ALTech) Younkwang Jung Note Added: 0006267
2021-03-10 11:05 (SW) Kerwin Chen Note Added: 0006278
2021-03-10 13:14 (ALTech) Younkwang Jung Note Added: 0006283
2021-03-10 14:47 (SW) Kerwin Chen Note Added: 0006285
2021-03-10 15:06 (ALTech) Younkwang Jung Note Added: 0006288
2021-03-12 13:12 (ALTech) Younkwang Jung Note Added: 0006329
2021-03-19 10:21 (ALTech) Younkwang Jung Note Added: 0006449
2021-04-06 13:50 (ALTech) Younkwang Jung Note Added: 0006576
2021-04-06 14:39 (SW) Kerwin Chen Note Added: 0006578
2021-04-06 15:23 (ALTech) Younkwang Jung Note Added: 0006581
2021-04-06 16:05 (SW) Kerwin Chen Note Added: 0006584
2021-12-23 16:36 (SW) Kerwin Chen Assigned To (SW) Kerwin Chen => (ALTech) Younkwang Jung
2021-12-23 16:36 (SW) Kerwin Chen Status assigned => closed
2021-12-23 16:36 (SW) Kerwin Chen Resolution open => fixed
2021-12-23 16:36 (SW) Kerwin Chen Note Added: 0009057